--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> Are you terminating all your Timers and Threads that might be accessing the board before closing?
>  
> Regards
> TK
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, January 21, 2012 9:29 PM
> Subject: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>  
> Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > Brad/Tom,
> >
> > OK, at least I've got a work-around, so not a biggie.
> >
> > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> >
> > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> >
> > Any idea where I should look?
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > >
> > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > it out a while back as well.
> > >
> > >
> > >
> > > I think I have it fixed, but I need to test and upload new source.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > Behalf Of himykabibble
> > > Sent: Saturday, January 21, 2012 9:29 PM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > >
> > >
> > >
> > >
> > >
> > > Brad,
> > >
> > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > >
> > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > >
> > > Each button has an LED in it. The button click event handlers use the
> > > following to set or clear the I/O bits:
> > >
> > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > >
> > > This much works properly, and the bits toggle as they should.
> > >
> > > My 100mSec status loop does the following to get current status
> > >
> > > KMController.UpdateMainStatus();
> > >
> > > I then have functions that return the current status of the coolant I/Os
> > > using:
> > >
> > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > >
> > > These values are used to control the LEDs in the two buttons.
> > >
> > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > back as true. To get the correct status back, I have to do the following:
> > >
> > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> I believe so, but I'll make a second run through and check.
>
> This is *really* close to working....
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> >  
> > Regards
> > TK
> >
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, January 21, 2012 9:29 PM
> > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> >
> >
> >  
> > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > Brad/Tom,
> > >
> > > OK, at least I've got a work-around, so not a biggie.
> > >
> > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > >
> > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > >
> > > Any idea where I should look?
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > >
> > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > it out a while back as well.
> > > >
> > > >
> > > >
> > > > I think I have it fixed, but I need to test and upload new source.
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > > Behalf Of himykabibble
> > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Brad,
> > > >
> > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > >
> > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > >
> > > > Each button has an LED in it. The button click event handlers use the
> > > > following to set or clear the I/O bits:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > >
> > > > This much works properly, and the bits toggle as they should.
> > > >
> > > > My 100mSec status loop does the following to get current status
> > > >
> > > > KMController.UpdateMainStatus();
> > > >
> > > > I then have functions that return the current status of the coolant I/Os
> > > > using:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > >
> > > > These values are used to control the LEDs in the two buttons.
> > > >
> > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > back as true. To get the correct status back, I have to do the following:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Ray,
>
>
>
> Also worth noting is that I will occasionally get a rogue KmotionServer.exe
> process if I have a kflop plugged in with an app connected and my cpu
> hibernates.
>
>
>
> When this happens, I usually need to restart as the process cannot be
> terminated in the task manager.
>
>
>
>
>
> -Brad Murry
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> Behalf Of Brad Murry
> Sent: Sunday, January 22, 2012 2:16 AM
> To: DynoMotion@yahoogroups.com
> Subject: RE: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>
>
>
> For what it's worth, I can stop and start MM and the html app without
> crashing anything.
>
>
>
> -Brad
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> Behalf Of himykabibble
> Sent: Saturday, January 21, 2012 11:15 PM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>
>
>
> Nope, I'm stopping all timers, and killing all threads I've created.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> "himykabibble" <jagboy@> wrote:
> >
> > Tom,
> >
> > I believe so, but I'll make a second run through and check.
> >
> > This is *really* close to working....
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> Tom Kerekes <tk@> wrote:
> > >
> > > Hi Ray,
> > > Â
> > > Are you terminating all your Timers and Threads that might be accessing
> the board before closing?
> > > Â
> > > Regards
> > > TK
> > >
> > > From: himykabibble <jagboy@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Saturday, January 21, 2012 9:29 PM
> > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > >
> > >
> > > Â
> > > Also, if I open my app, then open KMotion, then close my app, the board
> disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller
> in the FormClosing event handler. Is there something more I need to do to
> shutdown more gracefully?
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> , "himykabibble" <jagboy@> wrote:
> > > >
> > > > Brad/Tom,
> > > >
> > > > OK, at least I've got a work-around, so not a biggie.
> > > >
> > > > I am having another problem, related to disconnects. Using the
> combination of CheckIsReady() and Connected, I now seem to be reliably
> seeing connects and disconnects. At least I have yet to see it screw up.
> But, I'm finding that I can easily get things into a state where KMotion
> and/or dotNet appear to no longer work properly.
> > > >
> > > > If I have my app running, then disconnect the USB cable, the app
> correctly detects the disconnect. If I then re-connect the cable, the app
> correctly detects the reconnect, and the app mostly works properly. But, I
> can no longer control I/Os, and, at this point I can not even start up
> KMotion - it just hangs before putting anything up on the screen. Something
> in either KMotion or dotNet seems to be locking up.
> > > >
> > > > Any idea where I should look?
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com
> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > That is right Ray, the issue is with the MainStatus interop. Kevin
> pointed
> > > > > it out a while back as well.
> > > > >
> > > > >
> > > > >
> > > > > I think I have it fixed, but I need to test and upload new source.
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com
> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com
> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > Behalf Of himykabibble
> > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
>
> > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Brad,
> > > > >
> > > > > You seem to have a fencepose error in the I/O handling in dotNet. I
> have two
> > > > > buttons that control I/Os for Mist and Flood coolant, defined as
> follows:
> > > > >
> > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > >
> > > > > Each button has an LED in it. The button click event handlers use
> the
> > > > > following to set or clear the I/O bits:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > >
> > > > > This much works properly, and the bits toggle as they should.
> > > > >
> > > > > My 100mSec status loop does the following to get current status
> > > > >
> > > > > KMController.UpdateMainStatus();
> > > > >
> > > > > I then have functions that return the current status of the coolant
> I/Os
> > > > > using:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > >
> > > > > These values are used to control the LEDs in the two buttons.
> > > > >
> > > > > Here's the problem: I can correctly control the I/O pins. But, if I
> turn on
> > > > > the Mist, the Mist status comes back as false, and the Flood status
> comes
> > > > > back as true. To get the correct status back, I have to do the
> following:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > >
> > >
> >
>

 

Nope, I'm stopping all timers, and killing all threads I've created.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> I believe so, but I'll make a second run through and check.
>
> This is *really* close to working....
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> >  
> > Regards
> > TK
> >
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, January 21, 2012 9:29 PM
> > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> >
> >
> >  
> > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > Brad/Tom,
> > >
> > > OK, at least I've got a work-around, so not a biggie.
> > >
> > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > >
> > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > >
> > > Any idea where I should look?
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > >
> > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > it out a while back as well.
> > > >
> > > >
> > > >
> > > > I think I have it fixed, but I need to test and upload new source.
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > > Behalf Of himykabibble
> > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Brad,
> > > >
> > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > >
> > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > >
> > > > Each button has an LED in it. The button click event handlers use the
> > > > following to set or clear the I/O bits:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > >
> > > > This much works properly, and the bits toggle as they should.
> > > >
> > > > My 100mSec status loop does the following to get current status
> > > >
> > > > KMController.UpdateMainStatus();
> > > >
> > > > I then have functions that return the current status of the coolant I/Os
> > > > using:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > >
> > > > These values are used to control the LEDs in the two buttons.
> > > >
> > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > back as true. To get the correct status back, I have to do the following:
> > > >
> > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, TK <tk@...> wrote:
>
> Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
>
> Regards
>
> TK
>
> On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@...> wrote:
>
> > Nope, I'm stopping all timers, and killing all threads I've created.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > Tom,
> > >
> > > I believe so, but I'll make a second run through and check.
> > >
> > > This is *really* close to working....
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Ray,
> > > > Â
> > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > Â
> > > > Regards
> > > > TK
> > > >
> > > > From: himykabibble <jagboy@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > >
> > > >
> > > > Â
> > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Brad/Tom,
> > > > >
> > > > > OK, at least I've got a work-around, so not a biggie.
> > > > >
> > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > >
> > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > >
> > > > > Any idea where I should look?
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > it out a while back as well.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > > > > Behalf Of himykabibble
> > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > >
> > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > >
> > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > following to set or clear the I/O bits:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > >
> > > > > > This much works properly, and the bits toggle as they should.
> > > > > >
> > > > > > My 100mSec status loop does the following to get current status
> > > > > >
> > > > > > KMController.UpdateMainStatus();
> > > > > >
> > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > using:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > >
> > > > > > These values are used to control the LEDs in the two buttons.
> > > > > >
> > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Tom/Ray
>
> If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
>
>
>
> The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
>
>
>
> This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of TK
> Sent: Sunday, January 22, 2012 9:51 AM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>
>
>
> Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
>
>
>
> Regards
>
>
> TK
>
>
> On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@...> wrote:
>
>
>
> Nope, I'm stopping all timers, and killing all threads I've created.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> >
> > Tom,
> >
> > I believe so, but I'll make a second run through and check.
> >
> > This is *really* close to working....
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > >
> > > Hi Ray,
> > > Â
> > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > Â
> > > Regards
> > > TK
> > >
> > > From: himykabibble <jagboy@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Saturday, January 21, 2012 9:29 PM
> > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > >
> > >
> > > Â
> > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > >
> > > > Brad/Tom,
> > > >
> > > > OK, at least I've got a work-around, so not a biggie.
> > > >
> > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > >
> > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > >
> > > > Any idea where I should look?
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > it out a while back as well.
> > > > >
> > > > >
> > > > >
> > > > > I think I have it fixed, but I need to test and upload new source.
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > Behalf Of himykabibble
> > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Brad,
> > > > >
> > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > >
> > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > >
> > > > > Each button has an LED in it. The button click event handlers use the
> > > > > following to set or clear the I/O bits:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > >
> > > > > This much works properly, and the bits toggle as they should.
> > > > >
> > > > > My 100mSec status loop does the following to get current status
> > > > >
> > > > > KMController.UpdateMainStatus();
> > > > >
> > > > > I then have functions that return the current status of the coolant I/Os
> > > > > using:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > >
> > > > > These values are used to control the LEDs in the two buttons.
> > > > >
> > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > back as true. To get the correct status back, I have to do the following:
> > > > >
> > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Ray,
>
>
>
> I was referring to using the Release version instead of the Debug with respect to your KMotion references.
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> Sent: Sunday, January 22, 2012 10:51 AM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>
>
>
> Brad,
>
> Everything I'm using is from v428. It's the only version I have on my machine.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> >
> > Tom/Ray
> >
> > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> >
> >
> >
> > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> >
> >
> >
> > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > Sent: Sunday, January 22, 2012 9:51 AM
> > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> >
> >
> >
> >
> >
> > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> >
> >
> >
> > Regards
> >
> >
> > TK
> >
> >
> > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> >
> >
> >
> > Nope, I'm stopping all timers, and killing all threads I've created.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > >
> > > Tom,
> > >
> > > I believe so, but I'll make a second run through and check.
> > >
> > > This is *really* close to working....
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Ray,
> > > > Â
> > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > Â
> > > > Regards
> > > > TK
> > > >
> > > > From: himykabibble <jagboy@>
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > >
> > > >
> > > > Â
> > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Brad/Tom,
> > > > >
> > > > > OK, at least I've got a work-around, so not a biggie.
> > > > >
> > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > >
> > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > >
> > > > > Any idea where I should look?
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > it out a while back as well.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > Behalf Of himykabibble
> > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > >
> > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > >
> > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > following to set or clear the I/O bits:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > >
> > > > > > This much works properly, and the bits toggle as they should.
> > > > > >
> > > > > > My 100mSec status loop does the following to get current status
> > > > > >
> > > > > > KMController.UpdateMainStatus();
> > > > > >
> > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > using:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > >
> > > > > > These values are used to control the LEDs in the two buttons.
> > > > > >
> > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > >
> > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> I have one reference to the dotNet dll, and it is the release version.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Ray,
> >
> >
> >
> > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > Sent: Sunday, January 22, 2012 10:51 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> >
> >
> >
> >
> >
> > Brad,
> >
> > Everything I'm using is from v428. It's the only version I have on my machine.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > >
> > > Tom/Ray
> > >
> > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > >
> > >
> > >
> > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > >
> > >
> > >
> > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > Sent: Sunday, January 22, 2012 9:51 AM
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > >
> > >
> > >
> > >
> > >
> > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > >
> > >
> > >
> > > Regards
> > >
> > >
> > > TK
> > >
> > >
> > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > >
> > >
> > >
> > > Nope, I'm stopping all timers, and killing all threads I've created.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > >
> > > > Tom,
> > > >
> > > > I believe so, but I'll make a second run through and check.
> > > >
> > > > This is *really* close to working....
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Ray,
> > > > > Â
> > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > Â
> > > > > Regards
> > > > > TK
> > > > >
> > > > > From: himykabibble <jagboy@>
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > > Â
> > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > >
> > > > > > Brad/Tom,
> > > > > >
> > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > >
> > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > >
> > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > >
> > > > > > Any idea where I should look?
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > >
> > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > it out a while back as well.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > Behalf Of himykabibble
> > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Brad,
> > > > > > >
> > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > >
> > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > >
> > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > following to set or clear the I/O bits:
> > > > > > >
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > >
> > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > >
> > > > > > > My 100mSec status loop does the following to get current status
> > > > > > >
> > > > > > > KMController.UpdateMainStatus();
> > > > > > >
> > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > using:
> > > > > > >
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > >
> > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > >
> > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > >
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> It likely you are attaching your handler multiple times.
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> Sent: Sunday, January 22, 2012 11:17 AM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Re: Twiddling Bits in dotNet
>
>
>
>
>
> Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> >
> > Brad,
> >
> > I have one reference to the dotNet dll, and it is the release version.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > >
> > > Ray,
> > >
> > >
> > >
> > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > Sent: Sunday, January 22, 2012 10:51 AM
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > >
> > >
> > >
> > >
> > >
> > > Brad,
> > >
> > > Everything I'm using is from v428. It's the only version I have on my machine.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > >
> > > > Tom/Ray
> > > >
> > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > >
> > > >
> > > >
> > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > >
> > > >
> > > >
> > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > >
> > > > TK
> > > >
> > > >
> > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > >
> > > >
> > > >
> > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Tom,
> > > > >
> > > > > I believe so, but I'll make a second run through and check.
> > > > >
> > > > > This is *really* close to working....
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Ray,
> > > > > > ÃÆ'‚
> > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > ÃÆ'‚
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > > From: himykabibble <jagboy@>
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > > ÃÆ'‚
> > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > >
> > > > > > > Brad/Tom,
> > > > > > >
> > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > >
> > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > >
> > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > >
> > > > > > > Any idea where I should look?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > >
> > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > it out a while back as well.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > Behalf Of himykabibble
> > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Brad,
> > > > > > > >
> > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > >
> > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > >
> > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > following to set or clear the I/O bits:
> > > > > > > >
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > >
> > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > >
> > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > >
> > > > > > > > KMController.UpdateMainStatus();
> > > > > > > >
> > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > using:
> > > > > > > >
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > >
> > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > >
> > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > >
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> It happens one time, in the form constructor....
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > It likely you are attaching your handler multiple times.
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > Sent: Sunday, January 22, 2012 11:17 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> >
> >
> >
> >
> >
> > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > >
> > > Brad,
> > >
> > > I have one reference to the dotNet dll, and it is the release version.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > >
> > > > Ray,
> > > >
> > > >
> > > >
> > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Brad,
> > > >
> > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > Tom/Ray
> > > > >
> > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > >
> > > > >
> > > > >
> > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > >
> > > > >
> > > > >
> > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > >
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > >
> > > > > TK
> > > > >
> > > > >
> > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > >
> > > > >
> > > > >
> > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > >
> > > > > > Tom,
> > > > > >
> > > > > > I believe so, but I'll make a second run through and check.
> > > > > >
> > > > > > This is *really* close to working....
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Hi Ray,
> > > > > > > ÃÆ'‚
> > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > ÃÆ'‚
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > > From: himykabibble <jagboy@>
> > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > >
> > > > > > >
> > > > > > > ÃÆ'‚
> > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > >
> > > > > > > > Brad/Tom,
> > > > > > > >
> > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > >
> > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > >
> > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > >
> > > > > > > > Any idea where I should look?
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > >
> > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > it out a while back as well.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -Brad Murry
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > Behalf Of himykabibble
> > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Brad,
> > > > > > > > >
> > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > >
> > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > >
> > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > >
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > >
> > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > >
> > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > >
> > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > >
> > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > using:
> > > > > > > > >
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > >
> > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > >
> > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > >
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Oops! That is what was happening. I made an ill-conceived change in the process of trying to debug this that had an unanticipated side-effect of doing exactly that. So, that one is stomped. Thanks!
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > Brad,
> >
> > It happens one time, in the form constructor....
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > >
> > > It likely you are attaching your handler multiple times.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > > Sent: Sunday, January 22, 2012 11:17 AM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > >
> > >
> > >
> > >
> > >
> > > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > >
> > > > Brad,
> > > >
> > > > I have one reference to the dotNet dll, and it is the release version.
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > Ray,
> > > > >
> > > > >
> > > > >
> > > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Brad,
> > > > >
> > > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > Tom/Ray
> > > > > >
> > > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > > >
> > > > > >
> > > > > >
> > > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > > >
> > > > > >
> > > > > >
> > > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > >
> > > > > > TK
> > > > > >
> > > > > >
> > > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > >
> > > > > > > Tom,
> > > > > > >
> > > > > > > I believe so, but I'll make a second run through and check.
> > > > > > >
> > > > > > > This is *really* close to working....
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > > >
> > > > > > > > Hi Ray,
> > > > > > > > ÃÆ'‚
> > > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > > ÃÆ'‚
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > >
> > > > > > > > From: himykabibble <jagboy@>
> > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'‚
> > > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > >
> > > > > > > > > Brad/Tom,
> > > > > > > > >
> > > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > > >
> > > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > > >
> > > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > > >
> > > > > > > > > Any idea where I should look?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > >
> > > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > > it out a while back as well.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -Brad Murry
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > > Behalf Of himykabibble
> > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Brad,
> > > > > > > > > >
> > > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > > >
> > > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > >
> > > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > > >
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > >
> > > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > > >
> > > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > > >
> > > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > > >
> > > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > > using:
> > > > > > > > > >
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > >
> > > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > > >
> > > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > > >
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Ray L.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> OK, I've figured out what's causing the crash, just need to figure out why.... If I disable my WCF server, the crash does not occur, so I'm doing something wrong in handling that thread. Odd that it would affect KMotion, since it has nothing to do with KMotion - it's just providing a simple tcp port server for the toolpath display.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > Oops! That is what was happening. I made an ill-conceived change in the process of trying to debug this that had an unanticipated side-effect of doing exactly that. So, that one is stomped. Thanks!
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > Brad,
> > >
> > > It happens one time, in the form constructor....
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > >
> > > > It likely you are attaching your handler multiple times.
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > > > Sent: Sunday, January 22, 2012 11:17 AM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Brad,
> > > > >
> > > > > I have one reference to the dotNet dll, and it is the release version.
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > Ray,
> > > > > >
> > > > > >
> > > > > >
> > > > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > >
> > > > > > > Tom/Ray
> > > > > > >
> > > > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Regards
> > > > > > >
> > > > > > >
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > >
> > > > > > > > Tom,
> > > > > > > >
> > > > > > > > I believe so, but I'll make a second run through and check.
> > > > > > > >
> > > > > > > > This is *really* close to working....
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > > > >
> > > > > > > > > Hi Ray,
> > > > > > > > > ÃÆ'‚
> > > > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > > > ÃÆ'‚
> > > > > > > > > Regards
> > > > > > > > > TK
> > > > > > > > >
> > > > > > > > > From: himykabibble <jagboy@>
> > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'‚
> > > > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > >
> > > > > > > > > > Brad/Tom,
> > > > > > > > > >
> > > > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > > > >
> > > > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > > > >
> > > > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > > > >
> > > > > > > > > > Any idea where I should look?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Ray L.
> > > > > > > > > >
> > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > > > it out a while back as well.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > -Brad Murry
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > > > Behalf Of himykabibble
> > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Brad,
> > > > > > > > > > >
> > > > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > > > >
> > > > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > >
> > > > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > > > >
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > >
> > > > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > > > >
> > > > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > > > >
> > > > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > > > >
> > > > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > > > using:
> > > > > > > > > > >
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > >
> > > > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > > > >
> > > > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > > > >
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Ray L.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> This does not, however, have anything to do with the slow-down after a re-connect. On re-connect, I'm doing nothing but re-loading my Init code, using:
>
> // Re-connected, so download our init.c
> Thread.Sleep(1000);
> String TheCFile = @"C:\My KFlop C Programs\KMotionCNC\KMotionCNCInit.c";
> KMController.CompileAndLoadCoff(1, TheCFile, true);
> KMController.WriteLine("Execute1");
> Thread.Sleep(1000);
>
> Is there something more I should be doing, or something wrong with this code? It works perfectly on the first connect event.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > OK, I've figured out what's causing the crash, just need to figure out why.... If I disable my WCF server, the crash does not occur, so I'm doing something wrong in handling that thread. Odd that it would affect KMotion, since it has nothing to do with KMotion - it's just providing a simple tcp port server for the toolpath display.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > Oops! That is what was happening. I made an ill-conceived change in the process of trying to debug this that had an unanticipated side-effect of doing exactly that. So, that one is stomped. Thanks!
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > >
> > > > Brad,
> > > >
> > > > It happens one time, in the form constructor....
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > It likely you are attaching your handler multiple times.
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > > > > Sent: Sunday, January 22, 2012 11:17 AM
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > I have one reference to the dotNet dll, and it is the release version.
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > >
> > > > > > > Ray,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Brad,
> > > > > > >
> > > > > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > >
> > > > > > > > Tom/Ray
> > > > > > > >
> > > > > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Regards
> > > > > > > >
> > > > > > > >
> > > > > > > > TK
> > > > > > > >
> > > > > > > >
> > > > > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > >
> > > > > > > > > Tom,
> > > > > > > > >
> > > > > > > > > I believe so, but I'll make a second run through and check.
> > > > > > > > >
> > > > > > > > > This is *really* close to working....
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Ray,
> > > > > > > > > > ÃÆ'‚
> > > > > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > > > > ÃÆ'‚
> > > > > > > > > > Regards
> > > > > > > > > > TK
> > > > > > > > > >
> > > > > > > > > > From: himykabibble <jagboy@>
> > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'‚
> > > > > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Ray L.
> > > > > > > > > >
> > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Brad/Tom,
> > > > > > > > > > >
> > > > > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > > > > >
> > > > > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > > > > >
> > > > > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > > > > >
> > > > > > > > > > > Any idea where I should look?
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Ray L.
> > > > > > > > > > >
> > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > > > > it out a while back as well.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > -Brad Murry
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > > > > Behalf Of himykabibble
> > > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Brad,
> > > > > > > > > > > >
> > > > > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > > > > >
> > > > > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > >
> > > > > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > > > > >
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > >
> > > > > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > > > > >
> > > > > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > > > > >
> > > > > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > > > > >
> > > > > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > > > > using:
> > > > > > > > > > > >
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > >
> > > > > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > > > > >
> > > > > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > > > > >
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > Ray L.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> I've found and fixed one recursion bug, and I'm now down to what appears may be a dotNet performance issue. My 100mSec display timer handler makes a call to UpdateMainStatus(), then uses the dotNet MainStatus functions to read status of a number of pins, and other things, to update the display. The UpdateMainStatus() call appears to be taking quite some time to execute, and is what is slowing things down for me. It also appears to be even slower after a disconnect and reconnect, and I'm not 100% certain yet, but the slowness seems to persists across multiple invocations of my app, if I don't reset the board. If I comment out the call, and simply return default values for all the MainStatus calls, the performance returns to what I would expect. This makes sense, since it was yesterday when I plumbed in the MainStatus as my primary feedback mechanism that things kinda went off the rails. Does this make sense? Should it be taking so long? I'm going to try to time the calls, and see what we're dealing with.
>
> At least the crashes are now gone!
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > This does not, however, have anything to do with the slow-down after a re-connect. On re-connect, I'm doing nothing but re-loading my Init code, using:
> >
> > // Re-connected, so download our init.c
> > Thread.Sleep(1000);
> > String TheCFile = @"C:\My KFlop C Programs\KMotionCNC\KMotionCNCInit.c";
> > KMController.CompileAndLoadCoff(1, TheCFile, true);
> > KMController.WriteLine("Execute1");
> > Thread.Sleep(1000);
> >
> > Is there something more I should be doing, or something wrong with this code? It works perfectly on the first connect event.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > OK, I've figured out what's causing the crash, just need to figure out why.... If I disable my WCF server, the crash does not occur, so I'm doing something wrong in handling that thread. Odd that it would affect KMotion, since it has nothing to do with KMotion - it's just providing a simple tcp port server for the toolpath display.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > >
> > > > Oops! That is what was happening. I made an ill-conceived change in the process of trying to debug this that had an unanticipated side-effect of doing exactly that. So, that one is stomped. Thanks!
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Brad,
> > > > >
> > > > > It happens one time, in the form constructor....
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > It likely you are attaching your handler multiple times.
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > > > > > Sent: Sunday, January 22, 2012 11:17 AM
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > >
> > > > > > > Brad,
> > > > > > >
> > > > > > > I have one reference to the dotNet dll, and it is the release version.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > >
> > > > > > > > Ray,
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -Brad Murry
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > > > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Brad,
> > > > > > > >
> > > > > > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > >
> > > > > > > > > Tom/Ray
> > > > > > > > >
> > > > > > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -Brad Murry
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > TK
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > >
> > > > > > > > > > Tom,
> > > > > > > > > >
> > > > > > > > > > I believe so, but I'll make a second run through and check.
> > > > > > > > > >
> > > > > > > > > > This is *really* close to working....
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Ray L.
> > > > > > > > > >
> > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Ray,
> > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > Regards
> > > > > > > > > > > TK
> > > > > > > > > > >
> > > > > > > > > > > From: himykabibble <jagboy@>
> > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Ray L.
> > > > > > > > > > >
> > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Brad/Tom,
> > > > > > > > > > > >
> > > > > > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > > > > > >
> > > > > > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > > > > > >
> > > > > > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > > > > > >
> > > > > > > > > > > > Any idea where I should look?
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > Ray L.
> > > > > > > > > > > >
> > > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > > > > > it out a while back as well.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > -Brad Murry
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > > > > > Behalf Of himykabibble
> > > > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brad,
> > > > > > > > > > > > >
> > > > > > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > > > > > >
> > > > > > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > > >
> > > > > > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > > > > > >
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > > >
> > > > > > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > > > > > >
> > > > > > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > > > > > >
> > > > > > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > > > > > >
> > > > > > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > > > > > using:
> > > > > > > > > > > > >
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > > >
> > > > > > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > > > > > >
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > Ray L.
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Uh-oh! This looks like a problem.... The UpdateStatus calls are taking an average of about 300 mSec. I need to get status considerably faster than that. Any ideas?
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > I've found and fixed one recursion bug, and I'm now down to what appears may be a dotNet performance issue. My 100mSec display timer handler makes a call to UpdateMainStatus(), then uses the dotNet MainStatus functions to read status of a number of pins, and other things, to update the display. The UpdateMainStatus() call appears to be taking quite some time to execute, and is what is slowing things down for me. It also appears to be even slower after a disconnect and reconnect, and I'm not 100% certain yet, but the slowness seems to persists across multiple invocations of my app, if I don't reset the board. If I comment out the call, and simply return default values for all the MainStatus calls, the performance returns to what I would expect. This makes sense, since it was yesterday when I plumbed in the MainStatus as my primary feedback mechanism that things kinda went off the rails. Does this make sense? Should it be taking so long? I'm going to try to time the calls, and see what we're dealing with.
> >
> > At least the crashes are now gone!
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > >
> > > This does not, however, have anything to do with the slow-down after a re-connect. On re-connect, I'm doing nothing but re-loading my Init code, using:
> > >
> > > // Re-connected, so download our init.c
> > > Thread.Sleep(1000);
> > > String TheCFile = @"C:\My KFlop C Programs\KMotionCNC\KMotionCNCInit.c";
> > > KMController.CompileAndLoadCoff(1, TheCFile, true);
> > > KMController.WriteLine("Execute1");
> > > Thread.Sleep(1000);
> > >
> > > Is there something more I should be doing, or something wrong with this code? It works perfectly on the first connect event.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > >
> > > > OK, I've figured out what's causing the crash, just need to figure out why.... If I disable my WCF server, the crash does not occur, so I'm doing something wrong in handling that thread. Odd that it would affect KMotion, since it has nothing to do with KMotion - it's just providing a simple tcp port server for the toolpath display.
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > > >
> > > > > Oops! That is what was happening. I made an ill-conceived change in the process of trying to debug this that had an unanticipated side-effect of doing exactly that. So, that one is stomped. Thanks!
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> > > > > >
> > > > > > Brad,
> > > > > >
> > > > > > It happens one time, in the form constructor....
> > > > > >
> > > > > > Regards,
> > > > > > Ray L.
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > > > > >
> > > > > > > It likely you are attaching your handler multiple times.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -Brad Murry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
> > > > > > > Sent: Sunday, January 22, 2012 11:17 AM
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Crikey! The further I get into this, the less sense it makes! After I "disable" the BlinkTimer by means of the Stop() method, I continue to get the Tick events! When I look into the underlying Timer, it shows Enabled=false. Even if I un-link my event handler (i.e. Timer.Tick -= BlinkTimerTick), the events STILL keep coming! How is this possible???
> > > > > > >
> > > > > > > Regards,
> > > > > > > Ray L.
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > >
> > > > > > > > Brad,
> > > > > > > >
> > > > > > > > I have one reference to the dotNet dll, and it is the release version.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Ray L.
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > >
> > > > > > > > > Ray,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I was referring to using the Release version instead of the Debug with respect to your KMotion references.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -Brad Murry
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of himykabibble
> > > > > > > > > Sent: Sunday, January 22, 2012 10:51 AM
> > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Brad,
> > > > > > > > >
> > > > > > > > > Everything I'm using is from v428. It's the only version I have on my machine.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Ray L.
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > >
> > > > > > > > > > Tom/Ray
> > > > > > > > > >
> > > > > > > > > > If you look at the dispose callbacks in the .net library, I am calling Free on each of the objects. By freeing the memory of the c++ objects, is this causing an issue?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > The other thing to look out for Ray is making sure you are using the same versions of KMotion.dll, etc…. in your app as KMotion.exe is.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > This means you should only be using the files in the KMotion4xx\Kmotion\Release folder
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -Brad Murry
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of TK
> > > > > > > > > > Sent: Sunday, January 22, 2012 9:51 AM
> > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > Subject: Re: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Well I guess I didn't ask the right question. Is everything terminated in a clean manner so no interactions with KMotion are left incomplete. Killing a thread might cause a problem. Better to signal the thread to terminate itself.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Regards
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > TK
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Jan 21, 2012, at 10:15 PM, "himykabibble" <jagboy@> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Nope, I'm stopping all timers, and killing all threads I've created.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Ray L.
> > > > > > > > > >
> > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Tom,
> > > > > > > > > > >
> > > > > > > > > > > I believe so, but I'll make a second run through and check.
> > > > > > > > > > >
> > > > > > > > > > > This is *really* close to working....
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Ray L.
> > > > > > > > > > >
> > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Ray,
> > > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > > Are you terminating all your Timers and Threads that might be accessing the board before closing?
> > > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > > Regards
> > > > > > > > > > > > TK
> > > > > > > > > > > >
> > > > > > > > > > > > From: himykabibble <jagboy@>
> > > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > > Subject: [DynoMotion] Re: Twiddling Bits in dotNet
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > ÃÆ'‚
> > > > > > > > > > > > Also, if I open my app, then open KMotion, then close my app, the board disconnects, and KMotion crashes. I am doing a Dispose on the KM_Controller in the FormClosing event handler. Is there something more I need to do to shutdown more gracefully?
> > > > > > > > > > > >
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > Ray L.
> > > > > > > > > > > >
> > > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , "himykabibble" <jagboy@> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Brad/Tom,
> > > > > > > > > > > > >
> > > > > > > > > > > > > OK, at least I've got a work-around, so not a biggie.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am having another problem, related to disconnects. Using the combination of CheckIsReady() and Connected, I now seem to be reliably seeing connects and disconnects. At least I have yet to see it screw up. But, I'm finding that I can easily get things into a state where KMotion and/or dotNet appear to no longer work properly.
> > > > > > > > > > > > >
> > > > > > > > > > > > > If I have my app running, then disconnect the USB cable, the app correctly detects the disconnect. If I then re-connect the cable, the app correctly detects the reconnect, and the app mostly works properly. But, I can no longer control I/Os, and, at this point I can not even start up KMotion - it just hangs before putting anything up on the screen. Something in either KMotion or dotNet seems to be locking up.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Any idea where I should look?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > Ray L.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > That is right Ray, the issue is with the MainStatus interop. Kevin pointed
> > > > > > > > > > > > > > it out a while back as well.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I think I have it fixed, but I need to test and upload new source.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > -Brad Murry
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> ] On
> > > > > > > > > > > > > > Behalf Of himykabibble
> > > > > > > > > > > > > > Sent: Saturday, January 21, 2012 9:29 PM
> > > > > > > > > > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com> <mailto:DynoMotion%40yahoogroups.com>
> > > > > > > > > > > > > > Subject: [DynoMotion] Twiddling Bits in dotNet
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Brad,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > You seem to have a fencepose error in the I/O handling in dotNet. I have two
> > > > > > > > > > > > > > buttons that control I/Os for Mist and Flood coolant, defined as follows:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > KMIO.Add("MistCoolant", new KM_IO(KMController, 3, "MistCoolant",
> > > > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > > > > KMIO.Add("FloodCoolant", new KM_IO(KMController, 4, "FloodCoolant",
> > > > > > > > > > > > > > KMotion_dotNet.IO_TYPE.DIGITAL_OUT));
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Each button has an LED in it. The button click event handlers use the
> > > > > > > > > > > > > > following to set or clear the I/O bits:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > This much works properly, and the bits toggle as they should.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > My 100mSec status loop does the following to get current status
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > KMController.UpdateMainStatus();
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I then have functions that return the current status of the coolant I/Os
> > > > > > > > > > > > > > using:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID);
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID);
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > These values are used to control the LEDs in the two buttons.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Here's the problem: I can correctly control the I/O pins. But, if I turn on
> > > > > > > > > > > > > > the Mist, the Mist status comes back as false, and the Flood status comes
> > > > > > > > > > > > > > back as true. To get the correct status back, I have to do the following:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["MistCoolant"].ID+1);
> > > > > > > > > > > > > > KMController.MainStatus.GetBitsState(KMIO["FloodCoolant"].ID+1);
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > Ray L.
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>